|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2030 (1996)
|
|
Title:
|
Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI
|
|
|
2.
|
Status of approval:
|
|
|
Informational RFC approved October 1996. Obsoleted by RFC 4330.
|
|
3.
|
Justification for the specific reference:
|
|
|
Although Informational and obsoleted by RFC 5905 (2010), ITU-T H.810 uses the specs in this RFC as the mechanism to synchronize time and coordinate time distribution in a large, diverse Internet operating at rates from mundane to light-wave over its WAN Interface. This document describes the Simple Network Time Protocol (SNTP) Version 4, which is an adaptation of the Network Time Protocol (NTP) also utilized by H.810 to synchronize computer clocks in the Internet. SNTP can be used when the ultimate performance of the full NTP implementation described in RFC 1305 is not needed or justified. ITU-T H.810 allows SNTP as a secondary means for synchronizing computer clocks used within the Continua architecture.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
N/A.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Informational RFC approved October 1996. Obsoleted by RFC 4330. Obsoletes RFC 1769. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Specification approved October 1996 and there is one Continua certified implementation that utilizes SMTP.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
N/A.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[COL94] Colella, R., R. Callon, E. Gardner, Y. Rekhter, "Guidelines for OSI NSAP allocation in the Internet", RFC 1629, NIST, May 1994./
/
[DAR81] Postel, J., "Internet Protocol", STD 5, RFC 791, USC Information Sciences Institute, September 1981./
/
[DEE89] Deering, S., "Host extensions for IP multicasting", STD 5, RFC 1112, Stanford University, August 1989./
/
[DEE96] Deering, S., R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 1883, Xerox and Ipsilon, January 1996./
/
[DOB91] Dobbins, K, W. Haggerty, C. Shue, "OSI connectionless transport services on top of UDP - Version: 1", RFC 1240, Open Software Foundation, June 1991./
/
[EAS95] Eastlake, D., 3rd., and C. Kaufman, "Domain Name System Security Extensions", Work in Progress./
/
[FUR94] Furniss, P., "Octet sequences for upper-layer OSI to support basic communications applications", RFC 1698, Consultant, October 1994.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
N/A.
|
|
